Systems and methods for social append

ABSTRACT

Some embodiments of the present invention include a method for providing social information of members of one or more social networks includes receiving a request for a social handle of a person via a social handle application programming interface (API), the request including contact information about the person, performing a search for the social handle of the person using the contact information, normalizing the social handle if it is not already normalized to generate a normalized social handle, storing the normalized social handle as being associated with the contact information, and providing the normalized social handle in a response to the request.

CLAIM OF PRIORITY

This application claims priority to Provisional U.S. Patent ApplicationNo. 61/869,309, filed on Aug. 23, 2013, entitled “SOCIAL APPEND” byMalygin et al., which is incorporated herein by reference in itsentirety and for all purposes.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

The present disclosure relates generally to data processing, and morespecifically relates to providing social information.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also be inventions.

The following detailed description is made with reference to thetechnology disclosed. Preferred implementations are described toillustrate the technology disclosed, not to limit its scope, which isdefined by the claims. Those of ordinary skill in the art will recognizea variety of equivalent variations on the description.

Social network providers such as Facebook, Twitter, LinkedIn, andGoogle+ have enabled their users to share a multitude of socialinformation with other users. The social information may providevaluable insight into the interests of the users including, for example,business sentiment for various consumer brands. There is a need for aneasy and consistent approach to provide the social informationon-demand.

BRIEF SUMMARY

For some embodiments, methods and systems for providing socialinformation of members of one or more social networks includes receivinga request for a social handle of a person via a social handleapplication programming interface (API), the request including contactinformation about the person, performing a search for the social handleof the person using the contact information, normalizing the socialhandle if it is not already normalized to generate a normalized socialhandle, storing the normalized social handle as being associated withthe contact information, and providing the normalized social handle as aresponse to the request.

For some embodiments, methods and systems for providing socialinformation of members of one or more social networks includes receivinga request for a social handle of a person via a social handleapplication programming interface (API), the request including contactinformation about the person, matching the contact information receivedvia the request with stored contact information to find a storednormalized social handle, and providing the stored normalized socialhandle as a response to the request.

Other aspects and advantages of the present invention can be seen onreview of the drawings, the detailed description and the claims, whichfollow.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve only toprovide examples of possible structures and process steps for thedisclosed techniques. These drawings in no way limit any changes in formand detail that may be made to embodiments by one skilled in the artwithout departing from the spirit and scope of the disclosure.

FIG. 1 shows a diagram of an example computer system 102 that may beused with some embodiments of the present invention.

FIG. 2 shows a diagram of an example network environment 200 that may beused with some embodiments of the present invention.

FIG. 3 shows an example of application modules that may be included in asystem that provides social handles, in accordance with someembodiments.

FIG. 4 shows block diagram of a social handle match module, performed inaccordance with some embodiments.

FIG. 5 shows block diagram of a social handle search module andnormalization module, performed in accordance with some embodiments.

FIG. 6 shows block diagram of a social handle management module,performed in accordance with some embodiments.

FIG. 7A shows a flowchart of an example process for transmitting astored normalized social handle to a requester, performed in accordancewith some embodiments.

FIG. 7B shows a flowchart of an example process for searching for socialhandle URL in response to a request for a social handle, performed inaccordance with some embodiments.

FIG. 8A shows a system diagram 800 illustrating architectural componentsof an applicable environment, in accordance with some embodiments.

FIG. 8B shows a system diagram further illustrating architecturalcomponents of an applicable environment, in accordance with someembodiments.

FIG. 9 shows a system diagram 910 illustrating the architecture of amultitenant database environment, in accordance with some embodiments.

FIG. 10 shows a system diagram 910 further illustrating the architectureof a multitenant database environment, in accordance with someembodiments.

DETAILED DESCRIPTION

Applications of systems and methods according to one or more embodimentsare described in this section. These examples are being provided solelyto add context and aid in the understanding of the present disclosure.It will thus be apparent to one skilled in the art that the techniquesdescribed herein may be practiced without some or all of these specificdetails. In other instances, well known process steps have not beendescribed in detail in order to avoid unnecessarily obscuring thepresent disclosure. Other applications are possible, such that thefollowing examples should not be taken as definitive or limiting eitherin scope or setting.

In the following detailed description, references are made to theaccompanying drawings, which form a part of the description and in whichare shown, by way of illustration, specific embodiments. Although theseembodiments are described in sufficient detail to enable one skilled inthe art to practice the disclosure, it is understood that these examplesare not limiting, such that other embodiments may be used and changesmay be made without departing from the spirit and scope of thedisclosure.

As used herein, the term “multi-tenant database system” refers to thosesystems in which various elements of hardware and software of thedatabase system may be shared by one or more customers. For example, agiven application server may simultaneously process requests for a greatnumber of customers, and a given database table may store rows for apotentially much greater number of customers.

The described subject matter may be implemented in the context of anycomputer-implemented system, such as a software-based system, a databasesystem, a multi-tenant environment, or the like. Moreover, the describedsubject matter may be implemented in connection with two or moreseparate and distinct computer-implemented systems that cooperate andcommunicate with one another. One or more embodiments may be implementedin numerous ways, including as a process, an apparatus, a system, adevice, a method, a computer readable medium such as a computer readablestorage medium containing computer readable instructions or computerprogram code, or as a computer program product comprising a computerusable medium having a computer readable program code embodied therein.

A social handle may be a link associated with a social network provider(e.g., LinkedIn, Facebook, Twitter, etc.). A social handle may beassociated with social information of a person who is a member of asocial network provider. When a social handle is selected, the socialinformation of the person may be accessible. It may be possible that aperson has multiple social handles with the same social networkprovider. It may be possible that a person has a social handle with onesocial network provider and another social handle with another socialnetwork provider. Although the term “person” is used to associate with asocial handle, it is possible that the “person” may be an entity.

The disclosed embodiments may include methods of providing socialinformation and may include receiving a request for a social handle of aperson via a social handle application programming interface (API), therequest including contact information about the person, performing asearch for the social handle of the person using the contactinformation, normalizing the social handle if it is not alreadynormalized to generate a normalized social handle, storing thenormalized social handle as being associated with the contactinformation, and providing the normalized social handle as a response tothe request.

The disclosed embodiments may include systems to providing socialinformation of members of social networks. The systems may include aprocessor and one or more stored sequences of instructions which, whenexecuted by the processor, cause the processor to receive, via a socialhandle application programming interface (API), a request for a socialhandle of a person, perform a search for the social handle of the personusing contact information provided with the request, normalize thesocial handle if it is not already normalized to generate a normalizedsocial handle, store the normalized social handle as being associatedwith the contact information, and provide the normalized social handleas a response to the request.

The disclosed embodiments may include a machine-readable medium carryingone or more sequences of instructions for providing social information,which instructions, when executed by one or more processors, cause theone or more processors to receive, via a social handle applicationprogramming interface (API), a request for a social handle of a person,perform a search for the social handle of the person using contactinformation provided with the request, normalize the social handle if itis not already normalized to generate a normalized social handle, storethe normalized social handle as being associated with the contactinformation, and provide the normalized social handle as a response tothe request.

The disclosed embodiments may be related to providing social handles foruse in a computer-implemented system. The described subject matter maybe implemented in the context of any computer-implemented system, suchas a software-based system, a database system, a multi-tenantenvironment, or the like. Moreover, the described subject matter may beimplemented in connection with two or more separate and distinctcomputer-implemented systems that cooperate and communicate with oneanother. One or more implementations may be implemented in numerousways, including as a process, an apparatus, a system, a device, amethod, a computer readable medium such as a computer readable storagemedium containing computer readable instructions or computer programcode, or as a computer program product comprising a computer usablemedium having a computer readable program code embodied therein.

FIG. 1 is a diagram of an example computer system that may be used withsome embodiments of the present invention. The computing system 102 maybe used to access information from a database (e.g., social handledatabase) that may store contact information and correspondingnormalized social handles.

The computer system 102 is only one example of a suitable computingsystem, such as a mobile computing system, and is not intended tosuggest any limitation as to the scope of use or functionality of thedesign. Neither should the computing system 102 be interpreted as havingany dependency or requirement relating to any one or combination ofcomponents illustrated. The design is operational with numerous othergeneral purpose or special purpose computing systems. Examples ofwell-known computing systems, environments, and/or configurations thatmay be suitable for use with the design include, but are not limited to,personal computers, server computers, hand-held or laptop devices,multiprocessor systems, microprocessor-based systems, set top boxes,programmable consumer electronics, mini-computers, mainframe computers,distributed computing environments that include any of the above systemsor devices, and the like. For example, the computing system 102 may beimplemented as a mobile computing system such as one that is configuredto run with an operating system (e.g., iOS) developed by Apple Inc. ofCupertino, Calif. or an operating system (e.g., Android) that isdeveloped by Google Inc. of Mountain View, Calif.

Some embodiments of the present invention may be described in thegeneral context of computing system executable instructions, such asprogram modules, being executed by a computer. Generally, programmodules include routines, programs, objects, components, datastructures, etc. that performs particular tasks or implement particularabstract data types. Those skilled in the art can implement thedescription and/or figures herein as computer-executable instructions,which can be embodied on any form of computing machine readable mediadiscussed below.

Some embodiments of the present invention may also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules may be located inboth local and remote computer storage media including memory storagedevices.

Referring to FIG. 1, the computing system 102 may include, but are notlimited to, a processing unit 120 having one or more processing cores, asystem memory 130, and a system bus 121 that couples various systemcomponents including the system memory 130 to the processing unit 120.The system bus 121 may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus, and alocal bus using any of a variety of bus architectures. By way ofexample, and not limitation, such architectures include IndustryStandard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus,Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA)locale bus, and Peripheral Component Interconnect (PCI) bus also knownas Mezzanine bus.

The computing system 102 typically includes a variety of computerreadable media. Computer readable media can be any available media thatcan be accessed by computing system 102 and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer readable media may store information suchas computer readable instructions, data structures, program modules orother data. Computer storage media include, but are not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disks (DVD) or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by computing system 102. Communication mediatypically embodies computer readable instructions, data structures, orprogram modules.

The system memory 130 may include computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 131and random access memory (RAM) 132. A basic input/output system (BIOS)133, containing the basic routines that help to transfer informationbetween elements within computing system 102, such as during start-up,is typically stored in ROM 131. RAM 132 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 120. By way of example, and notlimitation, FIG. 1 also illustrates operating system 134, applicationprograms 135, other program modules 136, and program data 137.

The computing system 102 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 1 also illustrates a hard disk drive 141 that reads from or writesto non-removable, nonvolatile magnetic media, a magnetic disk drive 151that reads from or writes to a removable, nonvolatile magnetic disk 152,and an optical disk drive 155 that reads from or writes to a removable,nonvolatile optical disk 156 such as, for example, a CD ROM or otheroptical media. Other removable/non-removable, volatile/nonvolatilecomputer storage media that can be used in the exemplary operatingenvironment include, but are not limited to, USB drives and devices,magnetic tape cassettes, flash memory cards, digital versatile disks,digital video tape, solid state RAM, solid state ROM, and the like. Thehard disk drive 141 is typically connected to the system bus 121 througha non-removable memory interface such as interface 140, and magneticdisk drive 151 and optical disk drive 155 are typically connected to thesystem bus 121 by a removable memory interface, such as interface 150.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 1, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputing system 102. In FIG. 1, for example, hard disk drive 141 isillustrated as storing operating system 144, application programs 145,other program modules 146, and program data 147. Note that thesecomponents can either be the same as or different from operating system134, application programs 135, other program modules 136, and programdata 137. The operating system 144, the application programs 145, theother program modules 146, and the program data 147 are given differentnumeric identification here to illustrate that, at a minimum, they aredifferent copies.

A user may enter commands and information into the computing system 102through input devices such as a keyboard 162, a microphone 163, and apointing device 161, such as a mouse, trackball or touch pad or touchscreen. Other input devices (not shown) may include a joystick, gamepad, scanner, or the like. These and other input devices are oftenconnected to the processing unit 120 through a user input interface 160that is coupled with the system bus 121, but may be connected by otherinterface and bus structures, such as a parallel port, game port or auniversal serial bus (USB). A monitor 191 or other type of displaydevice is also connected to the system bus 121 via an interface, such asa video interface 190. In addition to the monitor, computers may alsoinclude other peripheral output devices such as speakers 197 and printer196, which may be connected through an output peripheral interface 190.

The computing system 102 may operate in a networked environment usinglogical connections to one or more remote computers, such as a remotecomputer 180. The remote computer 180 may be a personal computer, ahand-held device, a server, a router, a network PC, a peer device orother common network node, and typically includes many or all of theelements described above relative to the computing system 102. Thelogical connections depicted in FIG. 1 include a local area network(LAN) 171 and a wide area network (WAN) 173, but may also include othernetworks. Such networking environments are commonplace in offices,enterprise-wide computer networks, intranets and the Internet.

When used in a LAN networking environment, the computing system 102 maybe connected to the LAN 171 through a network interface or adapter 170.When used in a WAN networking environment, the computing system 102typically includes a modem 172 or other means for establishingcommunications over the WAN 173, such as the Internet. The modem 172,which may be internal or external, may be connected to the system bus121 via the user-input interface 160, or other appropriate mechanism. Ina networked environment, program modules depicted relative to thecomputing system 102, or portions thereof, may be stored in a remotememory storage device. By way of example, and not limitation, FIG. 1illustrates remote application programs 185 as residing on remotecomputer 180. It will be appreciated that the network connections shownare exemplary and other means of establishing a communications linkbetween the computers may be used.

It should be noted that some embodiments of the present invention may becarried out on a computer system such as that described with respect toFIG. 1. However, some embodiments of the present invention may becarried out on a server, a computer devoted to message handling,handheld devices, or on a distributed system in which different portionsof the present design may be carried out on different parts of thedistributed computing system.

Another device that may be coupled with the system bus 121 is a powersupply such as a battery or a Direct Current (DC) power supply) andAlternating Current (AC) adapter circuit. The DC power supply may be abattery, a fuel cell, or similar DC power source needs to be rechargedon a periodic basis. The communication module (or modem) 172 may employa Wireless Application Protocol (WAP) to establish a wirelesscommunication channel. The communication module 172 may implement awireless networking standard such as Institute of Electrical andElectronics Engineers (IEEE) 802.11 standard, IEEE std. 802.11-1999,published by IEEE in 1999.

Examples of mobile computing systems may be a laptop computer, a tabletcomputer, a Netbook, a smart phone, a personal digital assistant, orother similar device with on board processing power and wirelesscommunications ability that is powered by a Direct Current (DC) powersource that supplies DC voltage to the mobile computing system and thatis solely within the mobile computing system and needs to be rechargedon a periodic basis, such as a fuel cell or a battery.

FIG. 2 shows a diagram of an example network environment that may beused with some embodiments of the present invention. Network environment200 includes computing systems 205 and 210. One or more of the computingsystems 205 and 210 may be a mobile computing system. The computingsystems 205 and 210 may be connected to the network 250 via a cellularconnection or via a Wi-Fi router (not shown). The network 250 may be theInternet. The computing systems 205 and 210 may be coupled with one ormore server computing systems 255 and 260 via the network 250. Arequester may use the computing system 205 and local application 208(e.g., browser) to connect to the server computing system 255 and loginto the application 257 (e.g., a Salesforce.com® application) torequest for a social handle. The requester may be a user or anapplication using a social handle API. For example, the application 215in the computing system 210 may populate the social handle API with thecontact information of a person and send the contact information to theserver computing system 255. The contact information may include a firstname and a last name of a person whose social handle is being requested.The server computing system 255 may be coupled to a database 258 whichmay be configured to store normalized social handles. The database 258may be referred to herein as a social handle database.

The server computing system 255 may be coupled with the server computingsystem 260. When the social handle database does not have a copy of therequested social handle, the server computing system 250 may request theserver computing system 260 to search for the requested social handle inthe network 250. The searching operations may be performed byapplication 265 in the server computing system 260. The application 265may also be configured to perform normalization of the social handlesfound in the network 250. The normalized social handles generated by theapplication 265 may be stored in the social handle database 258.

FIG. 3 shows an example of application modules that may be included in asystem that provides social handles, in accordance with someembodiments. System 300 includes a social handle search module 310, asocial handle normalization module 315, a social handle match module320, and a social handle management module 325. The social handle searchmodule 310 may be configured to search the network 250 to find socialhandles that correspond to the contact information received with therequest and via the social handle API. One or more of the applicationmodules 310-325 may be implemented in one server computing system or indifferent server computing systems. Although not shown, the system 300may be associated with the social handle database 258 to storenormalized social handles and corresponding contact information.

The social handle search module 310 may be configured to search for thesocial handles of a person based on the contact information received viathe social handle API. Following is example schema for the social handleAPI to transmit the contact information:

<contact> <companyName>Cisco Systems</companyName><email>lionel.lobo@cisco.com</email> <firstName>Lion</firstName><lastName>Lobo</lastName> ...... </contact>

The social handle search module 310 may search for publicly availablesocial handles. The search may be performed when the social handledatabase 258 does not have a copy of the requested social handle.Following is a Uniform Resource Locator (URL) example of a publiclyavailable social handle (referred to as a social handle URL) associatedwith the social network Facebook:

EXAMPLE 1

-   -   http://facebook.com/profile.php?id=100002453742790#/pages/arrowhead-general-insurance-agency-inc/206925925993353        Following is a social handle URL example associated with the        social network LinkedIn:

EXAMPLE 2

-   -   http://linkedin.com/company/simons-bitzer-&-associates?trk?ppro_cprof        As can be noted, both of the social handle URL examples shown        above include many special characters. They use different        formats and it's not easily decipherable which portion of the        social handle URL is more relevant.

The social handle normalization module 315 may be configured tonormalize the social handle URLs found by the social handle searchmodule 310. For some embodiments, the normalization operations maygenerate a unique “canonical”, “normal” or “standard” representation ofthe social handle URL representing a person or an entity. Thenormalization operations may remove characters from a social handle URL.A normalized social handle is a valid URL that represents the samesocial information as the corresponding social handle URL. For someembodiments, in addition to the domain name, a normalized social handleincludes at least a portion of the social handle URL. Following is anexample normalized social handle that corresponds to the social handleURL shown in Example 1 above.

EXAMPLE 3

-   -   http://facebook.com/206925925993353        Following is an example normalized social handle that        corresponds to the social handle URL shown in Example 2 above.

EXAMPLE 4

-   -   http://linkedin.com/company/simons-bitzer-&-associates        As can be noted, each of the normalized social handles shown in        Example 3 and Example 4 is simpler than their corresponding        social handle URL shown in Example 1 and Example 2. A normalized        social handle generated by the social handle normalization        module 315 is unique to a person or an entity. The uniqueness of        the normalized social handle may help prevent duplicates.

The social handle match module 320 may be configured to match thecontact information received via the social handle API with informationstored in the social handle database 258. When a match exists, thesocial handle match module 320 may retrieve a copy of the requestedsocial handle from the social handle database 258 and transmit thesocial handle to the requester. A matching API may be used to transmitthe requested social handle to the requester. The matching API may beconfigured to enable the social handle match module 320 to transmit oneor more normalized social handles in a response to the requester. Theresponse may be in a particular format such as an eXtensible MarkupLanguage (XML) or JavaScript Object Notation (JSON) format. Following isexample schema for the matching API to transmit the social handles tothe requester:

<match> <matchedItems> <contact> <firstNamediff=″true″>Lionel</firstName> <lastName diff=″false″>Lobo</lastName><title diff=″true″>Engineering Manager</title> <email diff phonediff=″false″>+1.408.526.4000</phone> <contactIddiff=″true″>1345</contactId> ......=″false″>lionel.lobo@cisco.com</email> < <socialHandles> <handlesprovider=”FACEBOOK”> <handle> <url>www.facebook.com/123</url> <id>123</id> <handle> <handle> <url>www.facebook.com/abc</url> <id>abc</id> <handle> </handles> <handles provider=”TWITTER”> <handle><url>www.twitter.com/pnachnani</url> <id>pnachnani</id> <handle><handle> <url>www.twitter.com/abc</url>  <id>abc</id> <handle></handles> </socialHandles> </contact> </matchedItems>

For some embodiments, the normalized social handles associated with thesame social network provider may be grouped together when they are sentto the requester. For example, the normalized social handles associatedwith Facebook may be grouped separately from the normalized socialhandles associated with LinkedIn. Other information that may be sentinclude the social handle ID, the domain name of the social networkprovider, and any applicable comment related to normalized socialhandles. For some embodiments, there is no filtering of the socialhandles and all located social handles are sent to the requesterregardless of the social network provider. The requester may need todetermine which social handle to use and which to ignore in order toaccess the relevant social information. Following is a table that showsexample information that may be sent to the requester using the matchingAPI.

TABLE 1 Normalized Domain Social Handle Handle ID Comment Facebookhttp://facebook.com/206925925993353 206925925993353 Facebookhttp://facebook.com/siddo4ty4 siddo4ty4 LinkedInhttp://linkedin.com/in/domenicfenoglio in/domenicfenoglio LinkedInhttp://www.linkedin.com/pub/venkat- pub/venkat- maddela/4b/b07/773maddela/4b/b07/773 LinkedIn http://linkedin.com/in/domenicfenoglio/frin/domenicfenoglio/fr Language specific page Twitterhttp://twitter.com/pitneybowes pitneybowes Google+https://plus.google.com/ 116334694788096438740 116334694788096438740

For some embodiments, a contributing API may be provided to enable anapplication (e.g., administrator user interface shown in FIG. 6) tocontribute a social handle corresponding to a contact information. Thesocial handle contributed with the contributing API may not be anormalized social handle and may need to be normalized by the socialhandle normalization module 315 before being stored in the social handledatabase 258.

The social handle management module 325 may be configured to manage thesocial handles stored in the social handle database 258. The socialhandle management module 325 may be associated with an administratoruser interface to enable an administrator to perform the managementoperations. The social handle management module 325 may performoperations to accommodate privacy policies, keep the social handlesupdated, remove dead links, etc.

FIG. 4 shows block diagram of a social handle match module, performed inaccordance with some embodiments. The social handle match module 320 maybe coupled to the social handle database 258. When a request for asocial handle is received from a requester, the social handle matchmodule 320 may retrieve the contact information 405 from the socialhandle API 406. The social handle match module 320 may compare thecontact information 405 with contact information stored in the socialhandle database 258. When there is a match, the social handle 410corresponding to the contact information 405 may be retrieved from thesocial handle database 258. It may be possible that the social handlematch module 258 finds multiple matching social handles. This may bebecause a single contact information may be associated with multiplesocial handles from the same social network provider or from differentsocial network providers.

For some embodiments, when there are multiple matching social handle,each social handle may be assigned a confidence level. A confidencelevel may reflect whether the social handle found by the social handlematch module 320 is more likely or less likely what the requester isexpecting. The confidence level may be dependent on the quality of thecontact information. For example, if the contact information providedwith the social handle API is extensive and the social handle matchmodule 320 is able to find a social handle that represents a completematch, then the confidence level assigned to that social handle may behigh. If only a portion of the contact information is matched, then theconfidence level of the resulting social handle may not be high. Forsome embodiments, the social handle match module 320 may be configuredto transmit the social handles to the requester in an order based on theconfidence level. Referring to Table 1, the normalized social handle“http://facebook.com/206925925993353” may be associated with a higherconfidence level than the normalized social handle“http://facebook.com/siddo4ty4”.

FIG. 5 shows block diagram of a social handle search module andnormalization module, performed in accordance with some embodiments. Thesocial handle search module 310 may be coupled to the network 250. Whena request for a social handle is received from a requester, and thesocial handle match module 320 is not able to find a match in the socialhandle database 258, the social handle search module 310 may need tosearch the network 250 for a publicly available social handle based onthe contact information 405. The contact information 405 is included inthe social handle API 406. The social handle search module 310 may beable to locate one or more social handles 505. The social handle URL 505may be in a format provided by the associated social network providers.Examples of the social handle URL 505 are shown in Example 1 and Example2 above.

The social handle normalization module 315 may be configured to receivethe social handles 505 and normalized them to generate the normalizedsocial handles. Examples of the normalized social handles are shown inExample 3 and Example 4 above. The normalized social handle may bestored in the social handle database 258. For some embodiment, thenormalization operations performed by the social handle normalizationmodule 315 may identify a social handle identification (ID) that isembedded in the social handle URL.

The normalization operations are performed based on two set ofnormalization rules. The normalization rules in the first set can beapplied to all social handle URLs regardless of the associated socialnetwork provider. The normalization rules in the second set are groupedinto subsets, with the normalization rules in each subset to be appliedto the social handle URL of a different social network provider. Thenormalization rules in the first set may include removing the “http” or“https” from the social handle URL, and splitting the social handle URLby the question mark “?” if it exists into 2 parts, the left part issplit by “/” and right part is split by “&”. In general, when there is aredirect symbol such as “#!” or “#” in the social handle URL, the socialhandle ID can be found after the redirect symbol. Further, the socialhandle ID in the social handle URL is case-insensitive, and thereforecan be set in lower-case.

The normalization rules in the second set are grouped into a subset fora first social network provider (e.g., Facebook), a subset for a secondsocial network provider (e.g., LinkedIn), a subset for a third socialnetwork provider (e.g., Twitter), and a subset for a fourth socialnetwork provider (e.g., Google+). The number of subset may increase ifthere are more social network providers to provide their social handles.

Following are the normalization rules for the social network Facebook.For Facebook, the normalization rules are classified into four types -Plain, Profile, People and Pages. Following are for the normalizationrules for the Plain type of Facebook. For the Plain type, the socialhandle ID is located after the domain name and the slash “/” symbol. Forexample, if the social handle URL is “http://www.facebook.com/1234567”,then the social handle ID is “1234567”. If the social handle URLincludes a redirect sign such as “#!”, then the social handle ID isafter the redirect sign and after the slash. For example, if the socialhandle URL is “http://www.facebook.com/#!/Siddo4ty4”, then the socialhandle ID is “Siddo4ty4”. The social handle ID for the Plain type ofFacebook can be numeric or alphanumeric. Following are some examples ofnormalizing the social handle URL for the Plain type of Facebook:

Normalized Social Handle URL Social Handlehttp://www.facebook.com/keithwhite http://www.facebook.com/ keithwhitehttp://www.facebook.com/#!/Siddo4ty4 http://www.facebook.com/ Siddo4ty4

Following are for the normalization rules for the Profile type ofFacebook. For the Profile type, the social handle URL for the Profiletype has a keyword “profile.php?” as part of the URL, and the socialhandle ID is represented as key value pair and is numeric. Following aresome examples of normalizing the social handle URL for the Profile typeof Facebook:

Normalized Social Handle URL Social Handlehttp://www.facebook.com/profile.php? http://www.facebook.com/id=1247133407 1247133407 http://www.facebook.com/search.php?q=http://facebook.com/ Serge Doubinski&type=users#!/profile. 26208305php?id=26208305

Following are for the normalization rules for the People type ofFacebook. For the People type, the social handle URL has the keyword“people” as part of the URL, and the social handle ID is numeric.Following are some examples of normalizing the social handle URL for thePeople type of Facebook:

Normalized Social Handle URL Social Handlehttp://www.facebook.com/people/Kate- http://www.facebook.com/Lee/100001117817060 100001117817060

Following are for the normalization rules for the Page type of Facebook.For the Page type, the social handle URL has the keyword “pages” as partof the URL, and the social handle ID is numeric. Following are someexamples of normalizing the social handle URL for the Page type ofFacebook:

Normalized Social Handle URL Social Handlehttp://facebook.com/pages/Wilmington-NC/ http://facebook.com/NeoNexus-Corporation/ 81283078247 81283078247?ref=tshttp://facebook.com/pages/insideup/ http://facebook.com/ 168824503128720168824503128720 http://facebook.com/profile.php?id= http://facebook.com/100002453742790#/pages/ 206925925993353 arrowhead-general-insurance-agency-inc/ 206925925993353

Following are the normalization rules for the social network LinkedIn.For LinkedIn, the social handle URL usually include four keywords suchas “in”, “pub”, “company”, and “companies”. The other informationincluded in the social handle URL for LinkedIn is not used for thenormalization. Following are some examples of normalizing the socialhandle URL for LinkedIn:

Normalized Social Handle URL Social Handle http://linkedin.com/in/http://linkedin.com/in/ domenicfenoglio domenicfenogliohttp://www.linkedin.com/pub/ http://www.linkedin.com/pub/jeff-schindler/1b/7b0/178/ jeff-schindler/1b/7b0/178http://linkedin.com/ http://linkedin.com/company/company/simons-bitzer-&- simons-bitzer-&-associatesassociates?trk=ppro_cprof http://linkedin.com/companies/http://linkedin.com/companies/ 8291 8291

Following are the normalization rules for the social network LinkedInwith international domains. For the international domain, the countrycodes are used as subdomains for the domain LinkedIn.com (e.g.,uk.linkedin.com). The subdomain indicates a country, and potentially canbe used by LinkedIn for load-balancing geographically. The remainingportion of the social handle URL for international domain remains thesame whether the social handle URL is used with only the domain or withthe subdomain. Thus, when the subdomain is changed to reflect adifferent country for the same person, the social information remainsthe same. Locale or language specific pages may be created by adding thelocal code to the end of the domain. For example, a French profile pagemay be added to a social handle URL by adding “/fr” at the end of thesocial handle URL. This enables having a profile in a default languageand similar profiles in various languages. For normalization, thecountry code can be removed from the beginning of the social handle URL.For example, if the social handle URL is uk.linkedin.com, then it can benormalized to www.linkedin.com. When the social handle URL includes alocale identifier at the end, then each locale may be treated as adifferent social handle since the social information may be different.Following are some examples of normalizing the social handle URL forLinkedIn with international domain:

Normalized Social Handle URL Social Handle http://uk.linkedin.com/in/dhttp://linkedin.com/in/ omenicfenoglio domenicfenogliohttp://uk.linkedin.com/pub/ http://www.linkedin.com/pub/jeff-jeff-schindler/fr schindler/fr

Following are the normalization rules for the social network Twitter.For Twitter, the social handle URL usually include the symbol “@” at thebeginning of the social handle ID. The symbol “@” can be removed. Thesocial handle URL can include redirect symbol such as “#!”, and thesocial handle ID can be alpha-numeric. Following are some examples ofnormalizing the social handle URL for LinkedIn:

Normalized Social Handle URL Social Handlehttp%3A%2F%2Fwww.twitter.com%2Fegebhardt http://twitter.com/ egebhardthttp://twitter.com/#!/sharito241 http://twitter.com/ sharito241twitter.com/WindstreamBiz?cm_sp= http://twitter.com/Res2Biz-_-SelectorFooter-_-Twitter WindstreamBiz may be redirected to:http://twitter.com/#!/WindstreamBiz

Following are the normalization rules for the social network providerGoogle+. For Google+, the social handle ID attribute is numeric and thesocial handle URL may include redirect symbols. Following are someexamples of normalizing the social handle URL for Google+:

Normalized Social Handle URL Social Handle https://plus.google.com/https://plus.google.com/ 104891977700776502289 104891977700776502289

FIG. 6 shows block diagram of a social handle management module,performed in accordance with some embodiments. The social handlemanagement module 325 may be coupled to the social handle database 258and an administrator user interface 600. An administrator may use theadministrator user interface 600 to issue commands 602 to cause thesocial handle management module 325 to add a social handle, suppress asocial handle, un-suppress a social handle, delete a social handle, andunlink a contact. A known social handle may be added to the socialhandle database using the add-social handle module 605. This may beperformed using the contribute API discussed above. For privacypurposes, a social handle in the social handle database 258 may besuppressed from being accessed using the suppress module 610. When asocial handle is suppressed, it may not be included in the matching APIwhen a response is sent to the requester. When privacy is not an issue,a suppressed social handle may be un-suppressed using the un-suppressmodule 615. A social handle may also be deleted from the social handledatabase 258 using the delete module 620. This may be necessary, forexample, when it is determined that the social handle is not valid ordoes not represent the social information of an intended person orentity. A social handle may also be unlinked from a contact information.This may occur, for example, when it is determined that the socialhandle is not related to the contact information.

FIG. 7A shows a flowchart of an example process for transmitting astored normalized social handle to a requester, performed in accordancewith some embodiments. The method 700 may be used to enable acquiringsocial information of a person or an entity. At block 705, the socialhandle API is made available to enable a requester (e.g., customer,partner, and independent software vendor, or any entity) to request forthe social information of a person or an entity. At block 710, thecontact information is received from the requester via the social handleAPI. The contact information may include one or more of first name, lastname, email address, telephone number, company name, home address, etc.At block 715, the contact information may be used to determine if thereis a match with contact information in the social handle database 258.When there is a match, a stored and normalized social handlecorresponding to the contact information may be provided to therequester, as shown in block 720.

FIG. 7B shows a flowchart of an example process for searching for socialhandle URL in response to a request for a social handle, performed inaccordance with some embodiments. The method 722 may be used to enableacquiring social information of a person or an entity. At block 725, thesocial handle API is made available to enable a requester to request fora social handle. At block 730, the contact information is received fromthe requester via the social handle API. At block 735, the contactinformation may be used to determine if there is a match with contactinformation in the social handle database 258. When there isn't a match,a search is performed to find publicly available social handle URL usingthe contact information, as shown in block 740. One or more socialhandle URL may be found. At block 745, the social handle URLs found fromthe search are normalized to generate one or more normalized socialhandles. At block 750, the one or more normalized social handles arelinked with the contact information and stored in the social handledatabase 258. At block 755, the one or more normalized social handlesare sent to the requester.

FIG. 8A shows a system diagram 800 illustrating architectural componentsof an on-demand service environment, in accordance with someembodiments. A client machine located in the cloud 804 (or Internet) maycommunicate with the on-demand service environment via one or more edgerouters 808 and 812. The edge routers may communicate with one or morecore switches 820 and 824 via firewall 816. The core switches maycommunicate with a load balancer 828, which may distribute server loadover different pods, such as the pods 840 and 844. The pods 840 and 844,which may each include one or more servers and/or other computingresources, may perform data processing and other operations used toprovide on-demand services. Communication with the pods may be conductedvia pod switches 832 and 836. Components of the on-demand serviceenvironment may communicate with a database storage system 856 via adatabase firewall 848 and a database switch 852.

As shown in FIGS. 8A and 8B, accessing an on-demand service environmentmay involve communications transmitted among a variety of differenthardware and/or software components. Further, the on-demand serviceenvironment 800 is a simplified representation of an actual on-demandservice environment. For example, while only one or two devices of eachtype are shown in FIGS. 8A and 8B, some embodiments of an on-demandservice environment may include anywhere from one to many devices ofeach type. Also, the on-demand service environment need not include eachdevice shown in FIGS. 8A and 8B, or may include additional devices notshown in FIGS. 8A and 8B.

Moreover, one or more of the devices in the on-demand serviceenvironment 800 may be implemented on the same physical device or ondifferent hardware. Some devices may be implemented using hardware or acombination of hardware and software. Thus, terms such as “dataprocessing apparatus,” “machine,” “server” and “device” as used hereinare not limited to a single hardware device, but rather include anyhardware and software configured to provide the described functionality.

The cloud 804 is intended to refer to a data network or plurality ofdata networks, often including the Internet. Client machines located inthe cloud 804 may communicate with the on-demand service environment toaccess services provided by the on-demand service environment. Forexample, client machines may access the on-demand service environment toretrieve, store, edit, and/or process information.

In some embodiments, the edge routers 808 and 812 route packets betweenthe cloud 804 and other components of the on-demand service environment800. The edge routers 808 and 812 may employ the Border Gateway Protocol(BGP). The BGP is the core routing protocol of the Internet. The edgerouters 808 and 812 may maintain a table of IP networks or ‘prefixes’which designate network reachability among autonomous systems on theInternet.

In one or more embodiments, the firewall 816 may protect the innercomponents of the on-demand service environment 800 from Internettraffic. The firewall 816 may block, permit, or deny access to the innercomponents of the on-demand service environment 800 based upon a set ofrules and other criteria. The firewall 816 may act as one or more of apacket filter, an application gateway, a stateful filter, a proxyserver, or any other type of firewall.

In some embodiments, the core switches 820 and 824 are high-capacityswitches that transfer packets within the on-demand service environment800. The core switches 820 and 824 may be configured as network bridgesthat quickly route data between different components within theon-demand service environment. In some embodiments, the use of two ormore core switches 820 and 824 may provide redundancy and/or reducedlatency.

In some embodiments, the pods 840 and 844 may perform the core dataprocessing and service functions provided by the on-demand serviceenvironment. Each pod may include various types of hardware and/orsoftware computing resources. An example of the pod architecture isdiscussed in greater detail with reference to FIG. 8B.

In some embodiments, communication between the pods 840 and 844 may beconducted via the pod switches 832 and 836. The pod switches 832 and 836may facilitate communication between the pods 840 and 844 and clientmachines located in the cloud 804, for example via core switches 820 and824. Also, the pod switches 832 and 836 may facilitate communicationbetween the pods 840 and 844 and the database storage 856.

In some embodiments, the load balancer 828 may distribute workloadbetween the pods 840 and 844. Balancing the on-demand service requestsbetween the pods may assist in improving the use of resources,increasing throughput, reducing response times, and/or reducingoverhead. The load balancer 828 may include multilayer switches toanalyze and forward traffic.

In some embodiments, access to the database storage 856 may be guardedby a database firewall 848. The database firewall 848 may act as acomputer application firewall operating at the database applicationlayer of a protocol stack. The database firewall 848 may protect thedatabase storage 856 from application attacks such as structure querylanguage (SQL) injection, database rootkits, and unauthorizedinformation disclosure.

In some embodiments, the database firewall 848 may include a host usingone or more forms of reverse proxy services to proxy traffic beforepassing it to a gateway router. The database firewall 848 may inspectthe contents of database traffic and block certain content or databaserequests. The database firewall 848 may work on the SQL applicationlevel atop the TCP/IP stack, managing applications' connection to thedatabase or SQL management interfaces as well as intercepting andenforcing packets traveling to or from a database network or applicationinterface.

In some embodiments, communication with the database storage system 856may be conducted via the database switch 852. The multi-tenant databasesystem 856 may include more than one hardware and/or software componentsfor handling database queries. Accordingly, the database switch 852 maydirect database queries transmitted by other components of the on-demandservice environment (e.g., the pods 840 and 844) to the correctcomponents within the database storage system 856. In some embodiments,the database storage system 856 is an on-demand database system sharedby many different organizations. The on-demand database system mayemploy a multi-tenant approach, a virtualized approach, or any othertype of database approach. An on-demand database system is discussed ingreater detail with reference to FIGS. 9 and 10.

FIG. 8B shows a system diagram illustrating the architecture of the pod844, in accordance with one embodiment. The pod 844 may be used torender services to a user of the on-demand service environment 800.Insome embodiments, each pod may include a variety of servers and/or othersystems. The pod 844 includes one or more content batch servers 864,content search servers 868, query servers 872, file force servers 876,access control system (ACS) servers 880, batch servers 884, and appservers 888. Also, the pod 844 includes database instances 890, quickfile systems (QFS) 892, and indexers 894. In one or more embodiments,some or all communication between the servers in the pod 844 may betransmitted via the switch 836.

In some embodiments, the application servers 888 may include a hardwareand/or software framework dedicated to the execution of procedures(e.g., programs, routines, scripts) for supporting the construction ofapplications provided by the on-demand service environment 800 via thepod 844. Some such procedures may include operations for providing theservices described herein. The content batch servers 864 may requestsinternal to the pod. These requests may be long-running and/or not tiedto a particular customer. For example, the content batch servers 864 mayhandle requests related to log mining, cleanup work, and maintenancetasks.

The content search servers 868 may provide query and indexer functions.For example, the functions provided by the content search servers 868may allow users to search through content stored in the on-demandservice environment. The Fileforce servers 876 may manage requestsinformation stored in the Fileforce storage 878. The Fileforce storage878 may store information such as documents, images, and basic largeobjects (BLOBs). By managing requests for information using theFileforce servers 876, the image footprint on the database may bereduced.

The query servers 872 may be used to retrieve information from one ormore file systems. For example, the query system 872 may receiverequests for information from the app servers 888 and then transmitinformation queries to the NFS 896 located outside the pod. The pod 844may share a database instance 890 configured as a multi-tenantenvironment in which different organizations share access to the samedatabase. Additionally, services rendered by the pod 844 may requirevarious hardware and/or software resources. In some embodiments, the ACSservers 880 may control access to data, hardware resources, or softwareresources.

In some embodiments, the batch servers 884 may process batch jobs, whichare used to run tasks at specified times. Thus, the batch servers 884may transmit instructions to other servers, such as the app servers 888,to trigger the batch jobs. In some embodiments, the QFS 892 may be anopen source file system available from Sun Microsystems® of Santa Clara,Calif. The QFS may serve as a rapid-access file system for storing andaccessing information available within the pod 844. The QFS 892 maysupport some volume management capabilities, allowing many disks to begrouped together into a file system. File system metadata can be kept ona separate set of disks, which may be useful for streaming applicationswhere long disk seeks cannot be tolerated. Thus, the QFS system maycommunicate with one or more content search servers 868 and/or indexers894 to identify, retrieve, move, and/or update data stored in thenetwork file systems 896 and/or other storage systems.

In some embodiments, one or more query servers 872 may communicate withthe NFS 896 to retrieve and/or update information stored outside of thepod 844. The NFS 896 may allow servers located in the pod 844 to accessinformation to access files over a network in a manner similar to howlocal storage is accessed. In some embodiments, queries from the queryservers 822 may be transmitted to the NFS 896 via the load balancer 820,which may distribute resource requests over various resources availablein the on-demand service environment. The NFS 896 may also communicatewith the QFS 892 to update the information stored on the NFS 896 and/orto provide information to the QFS 892 for use by servers located withinthe pod 844.

In some embodiments, the pod may include one or more database instances890. The database instance 890 may transmit information to the QFS 892.When information is transmitted to the QFS, it may be available for useby servers within the pod 844 without requiring an additional databasecall. In some embodiments, database information may be transmitted tothe indexer 894. Indexer 894 may provide an index of informationavailable in the database 890 and/or QFS 892. The index information maybe provided to file force servers 876 and/or the QFS 892.

FIG. 9 shows a block diagram of an environment 910 wherein an on-demanddatabase service might be used, in accordance with some embodiments.Environment 910 includes an on-demand database service 916. User system912 may be any machine or system that is used by a user to access adatabase user system. For example, any of user systems 912 can be ahandheld computing system, a mobile phone, a laptop computer, a workstation, and/or a network of computing systems. As illustrated in FIGS.9 and 10, user systems 912 might interact via a network 914 with theon-demand database service 916.

An on-demand database service, such as system 916, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databaseservices may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS). Accordingly, “on-demand database service 916” and “system 916”will be used interchangeably herein. A database image may include one ormore database objects. A relational database management system (RDBMS)or the equivalent may execute storage and retrieval of informationagainst the database object(s). Application platform 918 may be aframework that allows the applications of system 916 to run, such as thehardware and/or software, e.g., the operating system. In animplementation, on-demand database service 916 may include anapplication platform 918 that enables creation, managing and executingone or more applications developed by the provider of the on-demanddatabase service, users accessing the on-demand database service viauser systems 912, or third party application developers accessing theon-demand database service via user systems 912.

One arrangement for elements of system 916 is shown in FIG. 9, includinga network interface 920, application platform 918, tenant data storage922 for tenant data 923, system data storage 924 for system data 925accessible to system 916 and possibly multiple tenants, program code 926for implementing various functions of system 916, and a process space928 for executing MTS system processes and tenant-specific processes,such as running applications as part of an application hosting service.Additional processes that may execute on system 916 include databaseindexing processes.

The users of user systems 912 may differ in their respective capacities,and the capacity of a particular user system 912 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a call center agent is using a particular user system 912to interact with system 916, the user system 912 has the capacitiesallotted to that call center agent. However, while an administrator isusing that user system to interact with system 916, that user system hasthe capacities allotted to that administrator. In systems with ahierarchical role model, users at one permission level may have accessto applications, data, and database information accessible by a lowerpermission level user, but may not have access to certain applications,database information, and data accessible by a user at a higherpermission level. Thus, different users may have different capabilitieswith regard to accessing and modifying application and databaseinformation, depending on a user's security or permission level.

Network 914 is any network or combination of networks of devices thatcommunicate with one another. For example, network 914 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network (e.g., the Internet), that network will be used in many of theexamples herein. However, it should be understood that the networks usedin some embodiments are not so limited, although TCP/IP is a frequentlyimplemented protocol.

User systems 912 might communicate with system 916 using TCP/IP and, ata higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 912 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 916. Such an HTTP server might be implemented asthe sole network interface between system 916 and network 914, but othertechniques might be used as well or instead. In some embodiments, theinterface between system 916 and network 914 includes load sharingfunctionality, such as round-robin HTTP request distributors to balanceloads and distribute incoming HTTP requests evenly over a plurality ofservers. At least as for the users that are accessing that server, eachof the plurality of servers has access to the MTS' data; however, otheralternative configurations may be used instead.

In some embodiments, system 916, shown in FIG. 9, implements a web-basedcustomer relationship management (CRM) system. For example, in someembodiments, system 916 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, web pages and other information to and fromuser systems 912 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject, however, tenant data typically is arranged so that data of onetenant is kept logically separate from that of other tenants so that onetenant does not have access to another tenant's data, unless such datais expressly shared. In certain embodiments, system 916 implementsapplications other than, or in addition to, a CRM application. Forexample, system 916 may provide tenant access to multiple hosted(standard and custom) applications. User (or third party developer)applications, which may or may not include CRM, may be supported by theapplication platform 918, which manages creation, storage of theapplications into one or more database objects and executing of theapplications in a virtual machine in the process space of the system916.

Each user system 912 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing system capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 912 typically runs an HTTP client, e.g., abrowsing program, such as Microsoft's Internet Explorer® browser,Mozilla's Firefox® browser, Opera's browser, or a WAP-enabled browser inthe case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g., subscriber of the multi-tenant database system)of user system 912 to access, process and view information, pages andapplications available to it from system 916 over network 914.

Each user system 912 also typically includes one or more user interfacedevices, such as a keyboard, a mouse, trackball, touch pad, touchscreen, pen or the like, for interacting with a graphical user interface(GUI) provided by the browser on a display (e.g., a monitor screen, LCDdisplay, etc.) in conjunction with pages, forms, applications and otherinformation provided by system 916 or other systems or servers. Forexample, the user interface device can be used to access data andapplications hosted by system 916, and to perform searches on storeddata, and otherwise allow a user to interact with various GUI pages thatmay be presented to a user. As discussed above, embodiments are suitablefor use with the Internet, which refers to a specific globalinternetwork of networks. However, it should be understood that othernetworks can be used instead of the Internet, such as an intranet, anextranet, a virtual private network (VPN), a non-TCP/IP based network,any LAN or WAN or the like.

According to some embodiments, each user system 912 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor or the like. Similarly, system 916(and additional instances of an MTS, where more than one is present) andall of their components might be operator configurable usingapplication(s) including computer code to run using a central processingunit such as processor system 917, which may include an Intel Pentium®processor or the like, and/or multiple processor units.

A computer program product implementation includes a machine-readablestorage medium (media) having instructions stored thereon/in which canbe used to program a computer to perform any of the processes of theembodiments described herein. Computer code for operating andconfiguring system 916 to intercommunicate and to process web pages,applications and other data and media content as described herein arepreferably downloaded and stored on a hard disk, but the entire programcode, or portions thereof, may also be stored in any other volatile ornon-volatile memory medium or device, such as a ROM or RAM, or providedon any media capable of storing program code, such as any type ofrotating media including floppy disks, optical discs, digital versatiledisk (DVD), compact disk (CD), microdrive, and magneto-optical disks,and magnetic or optical cards, nanosystems (including molecular memoryICs), or any type of media or device suitable for storing instructionsand/or data. Additionally, the entire program code, or portions thereof,may be transmitted and downloaded from a software source over atransmission medium, e.g., over the Internet, or from another server, ortransmitted over any other conventional network connection (e.g.,extranet, VPN, LAN, etc.) using any communication medium and protocols(e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.). It will also be appreciatedthat computer code for implementing embodiments can be implemented inany programming language that can be executed on a client system and/orserver or server system such as, for example, C, C++, HTML, any othermarkup language, Java™, JavaScript®, ActiveX®, any other scriptinglanguage, such as VB Script, and many other programming languages as arewell known may be used. (Java™ is a trademark of Sun Microsystems®,Inc.).

According to some embodiments, each system 916 is configured to provideweb pages, forms, applications, data and media content to user (client)systems 912 to support the access by user systems 912 as tenants ofsystem 916. As such, system 916 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another(e.g., in a server farm located in a single building or campus), or theymay be distributed at locations remote from one another (e.g., one ormore servers located in city A and one or more servers located in cityB). As used herein, each MTS could include logically and/or physicallyconnected servers distributed locally or across one or more geographiclocations.

Additionally, the term “server” is meant to include a computer system,including processing hardware and process space(s), and an associatedstorage system and database application (e.g., OODBMS or RDBMS) as iswell known in the art.

It should also be understood that “server system” and “server” are oftenused interchangeably herein. Similarly, the database object describedherein can be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 10 also shows a block diagram of environment 910 furtherillustrating system 916 and various interconnections, in accordance withsome embodiments. FIG. 10 shows that user system 912 may includeprocessor system 912A, memory system 912B, input system 912C, and outputsystem 912D. FIG. 10 shows network 914 and system 916. FIG. 10 alsoshows that system 916 may include tenant data storage 922, tenant data923, system data storage 924, system data 925, User Interface (UI) 1030,Application Program Interface (API) 1032, PL/SOQL 1034, save routines1036, application setup mechanism 1038, applications servers10001-1000N, system process space 1002, tenant process spaces 1004,tenant management process space 1010, tenant storage area 1012, userstorage 1014, and application metadata 1016. In other embodiments,environment 910 may not have the same elements as those listed aboveand/or may have other elements instead of, or in addition to, thoselisted above.

User system 912, network 914, system 916, tenant data storage 922, andsystem data storage 924 were discussed above in FIG. 9. Regarding usersystem 912, processor system 912A may be any combination of processors.Memory system 912B may be any combination of one or more memory devices,short term, and/or long term memory. Input system 912C may be anycombination of input devices, such as keyboards, mice, trackballs,scanners, cameras, and/or interfaces to networks. Output system 912D maybe any combination of output devices, such as monitors, printers, and/orinterfaces to networks. As shown by FIG. 10, system 916 may include anetwork interface 920 (of FIG. 9) implemented as a set of HTTPapplication servers 1000, an application platform 918, tenant datastorage 922, and system data storage 924. Also shown is system processspace 1002, including individual tenant process spaces 1004 and a tenantmanagement process space 1010. Each application server 1000 may beconfigured to tenant data storage 922 and the tenant data 923 therein,and system data storage 924 and the system data 925 therein to serverequests of user systems 912. The tenant data 923 might be divided intoindividual tenant storage areas 1012, which can be either a physicalarrangement and/or a logical arrangement of data. Within each tenantstorage area 1012, user storage 1014 and application metadata 1016 mightbe similarly allocated for each user. For example, a copy of a user'smost recently used (MRU) items might be stored to user storage 1014.Similarly, a copy of MRU items for an entire organization that is atenant might be stored to tenant storage area 1012. A UI 1030 provides auser interface and an API 1032 provides an application programmerinterface to system 916 resident processes to users and/or developers atuser systems 912. The tenant data and the system data may be stored invarious databases, such as Oracle™ databases.

Application platform 918 includes an application setup mechanism 1038that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage922 by save routines 1036 for execution by subscribers as tenant processspaces 1004 managed by tenant management process 1010 for example.Invocations to such applications may be coded using PL/SOQL 34 thatprovides a programming language style interface extension to API 1032. Adetailed description of some PL/SOQL language embodiments is discussedin commonly assigned U.S. Pat. No. 7,730,478, titled METHOD AND SYSTEMFOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA A MULTI-TENANTON-DEMAND DATABASE SERVICE, by Craig Weissman, filed Sep. 21, 2007,which is hereby incorporated by reference in its entirety and for allpurposes. Invocations to applications may be detected by systemprocesses, which manage retrieving application metadata 1016 for thesubscriber making the invocation and executing the metadata as anapplication in a virtual machine.

Each application server 1000 may be communicably coupled to databasesystems, e.g., having access to system data 925 and tenant data 923, viaa different network connection. For example, one application server10001 might be coupled via the network 914 (e.g., the Internet), anotherapplication server 1000N-1 might be coupled via a direct network link,and another application server 1000N might be coupled by yet a differentnetwork connection. Transfer Control Protocol and Internet Protocol(TCP/IP) are typical protocols for communicating between applicationservers 1000 and the database system. However, other transport protocolsmay be used to optimize the system depending on the network interconnectused.

In certain embodiments, each application server 1000 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 1000. In some embodiments, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 1000 and the user systems 912 to distribute requests to theapplication servers 1000. In some embodiments, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 1000. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain embodiments, three consecutive requests from the same user couldhit three different application servers 1000, and three requests fromdifferent users could hit the same application server 1000. In thismanner, system 916 is multi-tenant, wherein system 916 handles storageof, and access to, different objects, data and applications acrossdisparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each call center agent uses system 916 to manage theirsales process. Thus, a user might maintain contact data, leads data,customer follow-up data, performance data, goals and progress data,etc., all applicable to that user's personal sales process (e.g., intenant data storage 922). In an example of a MTS arrangement, since allof the data and the applications to access, view, modify, report,transmit, calculate, etc., can be maintained and accessed by a usersystem having nothing more than network access, the user can manage hisor her sales efforts and cycles from any of many different user systems.For example, if a call center agent is visiting a customer and thecustomer has Internet access in their lobby, the call center agent canobtain critical updates as to that customer while waiting for thecustomer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 916 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant specific data, system 916 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain embodiments, user systems 912 (which may be clientmachines/systems) communicate with application servers 1000 to requestand update system-level and tenant-level data from system 916 that mayrequire sending one or more queries to tenant data storage 922 and/orsystem data storage 924. System 916 (e.g., an application server 1000 insystem 916) automatically generates one or more SQL statements (e.g.,SQL queries) that are designed to access the desired information. Systemdata storage 924 may generate query plans to access the requested datafrom the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects according to some embodiments. It should be understood that“table” and “object” may be used interchangeably herein. Each tablegenerally contains one or more data categories logically arranged ascolumns or fields in a viewable schema. Each row or record of a tablecontains an instance of data for each category defined by the fields.For example, a CRM database may include a table that describes acustomer with fields for basic contact information such as name,address, phone number, fax number, etc. Another table might describe apurchase order, including fields for information such as customer,product, sale price, date, etc. In some multi-tenant database systems,standard entity tables might be provided for use by all tenants. For CRMdatabase applications, such standard entities might include tables foraccount, contact, lead, and opportunity data, each containingpre-defined fields. It should be understood that the word “entity” mayalso be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. U.S. Pat. No. 7,779,039, titledCUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASE SYSTEM, byWeissman, et al., and which is hereby incorporated by reference in itsentirety and for all purposes, teaches systems and methods for creatingcustom objects as well as customizing standard objects in a multi-tenantdatabase system. In some embodiments, for example, all custom entitydata rows are stored in a single multi-tenant physical table, which maycontain multiple logical tables per organization. In some embodiments,multiple “tables” for a single customer may actually be stored in onelarge table and/or in the same table as the data of other customers.

These and other aspects of the disclosure may be implemented by varioustypes of hardware, software, firmware, etc. For example, some featuresof the disclosure may be implemented, at least in part, bymachine-readable media that include program instructions, stateinformation, etc., for performing various operations described herein.Examples of program instructions include both machine code, such asproduced by a compiler, and files containing higher-level code that maybe executed by the computer using an interpreter. Examples ofmachine-readable media include, but are not limited to, magnetic mediasuch as hard disks, floppy disks, and magnetic tape; optical media suchas CD-ROM disks; magneto-optical media; and hardware devices that arespecially configured to store and perform program instructions, such asread-only memory devices (“ROM”) and random access memory (“RAM”).

While one or more embodiments and techniques are described withreference to an implementation in which a service cloud console isimplemented in a system having an application server providing a frontend for an on-demand database service capable of supporting multipletenants, the one or more embodiments and techniques are not limited tomulti-tenant databases nor deployment on application servers.Embodiments may be practiced using other database architectures, i.e.,ORACLE®, DB2® by IBM and the like without departing from the scope ofthe embodiments claimed.

Any of the above embodiments may be used alone or together with oneanother in any combination. Although various embodiments may have beenmotivated by various deficiencies with the prior art, which may bediscussed or alluded to in one or more places in the specification, theembodiments do not necessarily address any of these deficiencies. Inother words, different embodiments may address different deficienciesthat may be discussed in the specification. Some embodiments may onlypartially address some deficiencies or just one deficiency that may bediscussed in the specification, and some embodiments may not address anyof these deficiencies.

While various embodiments have been described herein, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of the present applicationshould not be limited by any of the embodiments described herein, butshould be defined only in accordance with the following andlater-submitted claims and their equivalents.

The invention claimed is:
 1. A computer-implemented method for providingsocial handles, the method comprising: receiving, by a server computingsystem in an on-demand service environment, a request for normalizedsocial handles, the request including contact information; determining,by the server computing system, whether one or more normalized socialhandles matching the contact information exists in a social handledatabase, the one or more normalized social handles corresponding topublicly available social handles provided by one or more socialnetworks; causing, by the server computing system, upon determining thatone or more matching normalized social handles do not exist in thesocial handle database, a search to be performed using the contactinformation to identify publicly available social handle uniformresource locators (URLs), each of the publicly available social handleURLs including a protocol identifier, special characters, and a socialhandle identification (ID) of an entity associated with the contactinformation embedded within the URL; modifying, by the server computingsystem, the identified public available social handle URLs by removingthe special characters embedded in the identified public availablesocial handle URLs and maintaining the protocol identifiers and socialhandle IDs embedded in the identified public available social handleURLs, each of the modified public available social handle URLs beingnormalized valid social handle URLs that includes the maintainedprotocol identifier, at least a portion of the identified publicavailable social handle URL, and the maintained social handle ID; andproviding, by the server computing system, the normalized socialhandles.
 2. The method of claim 1, further comprising: retrieving, upondetermining that one or more matching normalized social handles exist onthe social handle database, the one or more normalized social handlesfrom the social handle database.
 3. The method of claim 2, wherein anormalized social handle associated with a first social network isgenerated using a first format.
 4. The method of claim 3, wherein anormalized social handle associated with a second social network isgenerated using a second format.
 5. The method of claim 4, wherein theone or more normalized social handles are provided in the response basedon a confidence level order.
 6. The method of claim 4, wherein the oneor more normalized social handles are provided in the response based onsocial network grouping.
 7. A system for providing normalized socialhandles, the system comprising: a processor; and one or more storedsequences of instructions which, when executed by the processor, causethe processor to: receive a request for normalized social handles, therequest including contact information and received in an on-demandservice environment; determine whether one or more normalized socialhandles matching the contact information exists on a social handledatabase, the one or more normalized social handles corresponding topublicly available social handles provided by one or more socialnetworks; cause, upon determining that one or more matching normalizedsocial handles do not exist in the social handle database, a search tobe performed using the contact information to identify publiclyavailable social handle uniform resource locators (URLs), each of thepublicly available social handle URLs including a protocol identifier,special characters and a social handle identification (ID) of an entityassociated with the contact information; modify the identified publicavailable social handle URLs by removing the special characters embeddedin the identified public available social handle URLs and maintainingthe protocol identifiers and social handle IDs embedded in theidentified public available social handle URLs, each of the modifiedpublic available social handle URLs being normalized valid social handleURLs that includes the maintained protocol identifier, at least aportion of the identified public available social handle URL, and themaintained social handle ID; and provide the generated normalized socialhandles.
 8. The system of claim 7, wherein the processor is furtherconfigured to: retrieve, upon determining that one or more matchingnormalized social handles exist on the social handle database, the oneor more normalized social handles from the social handle database. 9.The system of claim 8, wherein a normalized social handle associatedwith a first social network is generated using a first format.
 10. Thesystem of claim 9, wherein a normalized social handle associated with asecond social network is generated using a second format.
 11. The systemof claim 10, wherein the one or more normalized social handles areprovided in the response based on a confidence level order.
 12. Thesystem of claim 10, wherein the one or more normalized social handlesare provided in the response based on social network grouping.
 13. Acomputer program product, comprising a non-transitory computer-readablemedium having a computer-readable program code embodied therein to beexecuted by one or more processors, the program code comprisinginstructions to: receive a request for normalized social handles, therequest including contact information and received in an on-demandservice environment; determine whether one or more normalized socialhandles matching the contact information exists on a social handledatabase, the one or more normalized social handles corresponding topublicly available social handles provided by one or more socialnetworks; cause, upon determining that one or more matching normalizedsocial handles do not exist in the social handle database, a search tobe performed using the contact information to identify publiclyavailable social handle uniform resource locators (URLs) , each of thepublicly available social handle URLs including a protocol identifier,special characters and a social handle identification (ID) of an entityassociated with the contact information; modify the identified publicavailable social handle URLs by removing the special characters fromeach of the identified public available social handle URLs, each of themodified public available social handle URLs being normalized validsocial handle URLs that include a protocol identifier and a socialhandle ID maintained from the identified public available social handleURL, and at least a portion of the identified public available socialhandle URL; and provide the generated normalized social handles.
 14. Thecomputer program product of claim 13, wherein the program code furthercomprising instructions to: retrieve, upon determining that one or morematching normalized social handles exist on the social handle database,the one or more normalized social handles from the social handledatabase.
 15. The computer program product of claim 14, wherein anormalized social handle associated with a first social network isgenerated using a first format.
 16. The computer program product ofclaim 15, wherein a normalized social handle associated with a secondsocial network is generated using a second format.
 17. The computerprogram product of claim 16, wherein the one or more normalized socialhandles are provided in the response based on at least one of aconfidence level order and a social network grouping.